Security - Before you go live
This article or section is in the process of an expansion or major restructuring. You are welcome to assist in its construction by editing it as well. If this article or section
Security FAQ - before you go live
This security list has been compiled from several sources, some of these sources are linked at the bottom of this article, as such you may find duplicate suggestions. DON'T skip anything because of this!
This list for the main part does not provide instructions it is only a list for you to check off each item as you perform the tasks.
- I Know this list will generate MANY questions, so please post to the Joomla.org Security forum
- Change database tables prefix from "jos_" to anything else.
- When changing this do not use any "reserved" prefixes such as bak_
- You may use numbers and letters and YES you may use more than 3 characters, so b37qm2_ is a valid name.
- Don't forget the underscore "_" as this makes it MUCH easier to read your table entries.
- It does not matter if your host does backups. Do it yourself too, and store them anywhere else other than the server.
- Backup up often! You would be amazed at how many sites NEVER perform regular backups.
- Did I mention to BACKUP your site?
Note: The extension Akeeba is highly recommended for backups.
- You find alternatives under the JED Backup Category
- Ask your server if they offer PHPsuExec, php_suexec or suPHP
- Use php.ini files if your server allows. With this you can disable functions that are not needed or dangerous
- Register_Globals = 0 (off) Many servers deafult this to ON.
- allow_url_fopen = 0 (off)
- expose_php = 0 (off)
- safe_mode = 0 (off)
- Use open_basedir , it limits which files/folders can be opened.
- Move configuration.php outside of your public directory.
- On file permissions, in general never use 777 if you don't know what you are doing (755 for directories and 644 for files is sensible for most). See FAQ: Verifying permissions
- Change username "admin" to anything else in Joomla, PhpBB, and anywhere else it used.
- Instead of renaming, you can also create a second super administrator account and remove the first. This way, the user id will be different.
- Change username or add password to username "root" in PhpMyAdmin. Default is NO password! This is not usually an issue on remote servers however if you have a local server it may be.
- Remove unused templates, extensions and unneeded files from your site. This includes compressed archives.
- Check joomla.org Vulnerable Extensions List (VEL)
- Check regularly for updates for Joomla, PHP, SQL and EVERY extension you use.
- Avoid encrypted code in extensions.
- Use some form of intrusion detection either through a cron job or an extension (like Eyesite).
- Check your log files OFTEN for unusual activity.
- Test your site for weaknesses or hire someone to perform this for you. Make sure you tell your host first what you are doing or you may get your site removed from the server!!!
- Use .htaccess to add extra protection to your administrator directory or use an extension (like kSecure)
- Get an SSL certificate for financial transactions and other sensitive data exchange.
- Change the paths (directories) where your log, temp (tmp) files are stored. Don't just move them, you have to change the setting in Global Config as well. You also have to ensure your new paths fall under the scope of open_basedir
- Don't save FTP user and password in your FTP tool of choice on your workstation (especially if you are on Windows).
- If you don't need them, don't enter the FTP user/password or remove them.
NOTE: If your administrator password is changed by hackers (or you forget it) follow this procedure to restore it: How do you recover your admin password?
- 7 Great tips from Marco Folio (Some with instructions)
- How to prevent an SQL injection by Marco Folio
- Joomla Security Primer by Tom Canavan
- Joomla.org Security Checklist Wiki
- Joomla.org Vulnerable Extensions List
Built from list by Ripose