The File Locker system is a part of the Hack Guard module of the Shield Security plugin.
It detects changes to the some of the most important WordPress files as they happen (in realtime). Then, lets you examine contents and revert as required.
The files covered with File Locker system are
- WP Config
- Root .htaccess
- Root index.php
WordPress File Locker is best explained in the release article here.
How does the File Locker system works?
The following is a brief outline to how Shield‘s WordPress File Locker system works:
- Shield scans your installation for your index.php, wp-config.php and .htaccess files in your top-level WordPress installation directory.
- For any files that are found, the Shield will request an OpenSSL Public Key from the ShieldNET API.
- If a public key is obtained from the API, Shield (on your site) makes a copy of the file contents and encrypts them using the public key, and stores it in your WordPress database.
- Shield will monitor these files and if they’re modified, or deleted, you’ll be alerted.
- You can then view the precise changes from within the Shield Scan section and compare them line-by-line.
- Once you’ve decided whether these changes are good, or bad, you can then accept the changes, or restore the file to its original state.
For example, let's say you want to lock your wp-config.php file.
The first thing to do is to go to the Hack Guard module => Realtime Change Detection => File Locker => and select WP Config option:
If this file is modified, you'll be alerted by email.
Important: To receive this type of email alert, please ensure that you have this enabled in the Reporting module of the plugin here.
Alert email will look like this (example):
Subject line: [Your Site Name] Site Report - Shield
Then, you can go to the Scans section => File Locker, and you'll see that this file is highlighted in red:
When you select this file to review, you'll be presented with the original and modified file content so you could compare them line-by-line. In this example, we have wp memory limit increased (modified) from the original 256M to 384M:
Now, you can decide whether you want to accept the change, or restore the file to its original state.
Once you've done that, this file will be highlighted in green, meaning that there is nothing to report: