View source for Security Checklist/Site Administration

{{RightTOC}}

== Site Administration ==

===Use well-formed passwords===
: Change passwords regularly and keep them unique. Use a random combination of letters, numbers, or symbols and avoid using single names or words found in a dictionary. Never use the names of your relatives, pets, etc. Search the forums for a script supplied by Wizzie that automatically changes passwords. This is a great tool for administrators or multiple sites.

===Follow a password leveling scheme===
: Most users may not need more than three levels of passwords and webmasters no more than five. Each level must be completely unrelated to the others in terms of which usernames and passwords are used.

===Maintain a strong site backup process===
: Never rely on others' backups. Take responsibility for your backup procedures. Many ISPs state in their contract that you can not rely solely on their backups.

===Monitor crack attempts===
: VPS and dedicated server users can run TripWire or SAMHAIN. These applications provide exhaustive file checking and reporting functionality, and can be installed in a stealthy manner to help protect themselves in the event of a serious infiltration. (Note: Users of shared servers can not use this technique.)</li>

===Perform automated intrusion detection===
: Use an Intrusion Prevention/Detection Systems to block/alert on malicious HTTP requests. 
* [http://www.google.com/search?q=Intrusion+Prevention Google search]

===Perform manual intrusion detection===
: Regularly check raw logs for suspicious activity. Don't rely on summaries and graphs.

===Stay current with security patches and upgrades===
: Apply vendor-released security patches ASAP.

===Proactively seek site vulnerabilities===
: Perform frequent web scanning.

* [http://www.google.com/search?q=%22web+scanning Google Search]

===Proactively seek SQL injections vulnerabilities===
: Use tools such as Paros Proxy for conducting automated SQL Injection tests against your PHP applications.
      <ul>
         <li>[http://www.google.com/search?q=%22SQL+Injection Google Search]</li>
         <li>[http://en.wikipedia.org/wiki/SQL_injection Wikipedia Article]</li>
      </ul>

===Use shell scripts to automate security tasks===
: Search the forums for these popular scripts:
      <ul>
           <li>Joomla! Version Checking</li>
           <li>Joomla! Component/Module Version Checking</li>
           <li>Exploit Checking</li>
      </ul>

===Learn about security software===
: There is not a single tool that can protect your site. If there were, it would be so heavily targeted that it would probably become a liability.

===Don't reinvent every wheel===
: Every now and then hire a professional Joomla! security consultant to review your configurations. Do you remember the adage, ''"Anyone who acts as their own lawyer has a fool for a client."'' The same goes for Web development. Don't expect to catch all of your own security mistakes.

== Go To Site Recovery ==
: When you're ready, continue on to [[Security Checklist 6 - Site Recovery]].


<!-- KEEP THIS AT THE END OF THE PAGE -->
[[Category:Security]]
[[Category:Security Checklist]]