Supported release and patches
Move off end-of-life Joomla and apply security releases on staging before production.
Security is not a plugin you install once. It is a supported release, sensible access, fewer extensions, correct server rules and a backup you have restored. Use this checklist to find the gaps that matter.
The public audit is not a penetration test. A hardening review needs administrator and hosting access.
Work from the platform outward: core, access, extensions, server, recovery.
Move off end-of-life Joomla and apply security releases on staging before production.
Remove unused admin accounts, use strong unique passwords and enable two-factor where supported.
Remove unused extensions, replace abandoned ones and check permissions on what remains.
Supported PHP, HTTPS, sensible security headers, correct file permissions and directory listing off.
Backups must be current, stored separately and tested by restoring to staging.
Log review, file monitoring and a named person who receives alerts and can act.
A practical order when time is limited.
Core, template and extensions on a supported release.
Remove stale admin users, enforce strong access and protect the login.
A failed restore is worse than no backup because it creates false confidence.
Who checks the logs, who calls the host and who decides to restore?
“They are very knowledgeable about Joomla!® and were very helpful throughout the project, even though we were not 100% sure about what we wanted to do.”
What hardening can and cannot promise.
Joomla can be run securely, but the install is only the starting point. Updates, access control, extensions, server rules and backups determine the real posture.
Keep the core and extensions supported and patched. Most avoidable incidents involve an outdated or abandoned entry point.
A security extension can help with monitoring and access rules, but it does not replace patching, least privilege and tested backups.
You can reduce exposure, but Joomla 3 is end of life and no longer receives official security patches. Hardening is not a substitute for moving to a supported release.
Pick the next question that matches your situation.
Run the public audit, then ask us to review access, extensions, backups and server rules against the checklist.