Skip to main content

File Changes (File Integrity Monitoring)

Introduction​

For any eCommerce website, the stability and security of your server's core files are non-negotiable. Unexpected modifications to critical files—such as configuration files, core platform scripts, or payment gateway integrations—can indicate a severe security breach, a hidden malware infection, or simply a botched developer deployment.

The File Changes feature in AuditIQ provides robust File Integrity Monitoring (FIM). It continuously tracks and records any alterations made to your server's file system. This allows merchants and agency development teams to instantly detect unauthorized access, pinpoint exactly when a crucial file was altered, and maintain a secure, compliant storefront.

Understanding Your File Integrity Data​

The dashboard provides a chronological, easy-to-read ledger of all detected server-level file events:

  • File: The absolute path on your server where the file is located (e.g., /var/www/html/app/etc/env.php or /public_html/wp-config.php). This tells you exactly which file was targeted.

  • Event: The specific action that occurred to the file. Common events include modified, created, or deleted.

  • Agent ID: The unique identifier of the internal AuditIQ monitoring agent that detected and logged the change.

  • Timestamp: The exact date and time the server-level event took place. Correlating this timestamp with known developer deployments or sudden site errors is crucial for rapid troubleshooting.

  • Full Log: A summary of the backend event attributes (such as changes to mtime or ctime).