2 ms·
As someone who has just gone through this process, it consists of a number of steps: - Whitelisting URL access in Nginx (though this can be circumvented since
by falcolas 12y ago
As someone who has just gone through this process, it consists of a number of steps:
- Whitelisting URL access in Nginx (though this can be circumvented since everything is ultimately executable through the root index.php, and there are a lot of intermediate URLs)
- Preventing writes to any portion of the WP install directory save uploads. Note - this breaks the option of automatic upgrades, but it prevents a lot of potential hacks.
- Overwriting theme portions you don't want to exist - for example even if never linked to, you can frequently access the comment page and get the default one. However, if you put in a comment theme PHP file and leave it more-or-less blank, you limit the potential harm coming from there.
- Disable many things in the settings.php file, like the cron, debug output, file_mod, etc.
- Cache as much of the output as possible.
- Block a bunch of the informational headers set by WordPress (though this only helps a bit; you can still identify the exact version of a WordPress site using fingerprinting)
- Run WPScanner against your site and plug those leaks.
- Limit what plugins you install to the bare minimum
- Keep everything up to date.
This is not comprehensive, and we're probably still at risk, but it's a start.