Technical review before ongoing maintenance
When taking over an existing site, we first map the installation. We need to know what exists, what is necessary and which parts would be difficult to restore.
- WordPress, theme and plugin versions
- Administrators and highly privileged accounts
- Backup location, history and restore capability
- PHP version, server environment, disk space and logs
- Unexpected files, hidden components and unnecessary plugins
Preventative maintenance
Updates should be controlled. Changes need to be traceable and a backup must exist before work that can affect the website.
- Planned updates and functional tests
- File and database backup
- Restricting administrators and protecting sensitive areas
- Checks for new PHP files, modified core files and abnormal behaviour
When an incident is suspected
We work methodically: preserve evidence, restrict access, identify persistence, restore clean components and change credentials. We then document what was found and which uncertainties remain.
- Logs and timeline
- Suspicious users, sessions and files
- Database changes and hidden administrators
- Cleanup, restoration and post-check
No serious supplier can promise that a WordPress site will “never be hacked”. The goal is to reduce risk, detect deviations earlier and restore with less damage.