There was a lot of importance given to the coding and running of WordPress in the last article on WordPress security. Listed below are four of the most important precautions that [url=http://www.intellixmedia.com/web-development.htm] Web Development[/url] need to take in order for WordPress blog to be secure.
Utilize strong passwords: This is an obvious good security practice, but too often forgotten. Make sure all your passwords are strong: your admin account, the ftp account and any other WordPress accounts that have any edit privileges. A simple web search will uncover stories telling you the best way to choose strong passwords. Instead of being redundant, let me just suggest that you read these pieces and consider what they say. Additionally, following their rules does not mean copying the choices!
Use SCP in lieu of FTP: The availability of good FTP programs makes transferring files to and from your hosting server onto your blog simple and convenient. If you can easily move files locally, most FTP programs will work for you. Search online for one that works for you. The problem with FTP is that your username and password is sent in clear text to your server. To be more secure you should use SCP instead. Here are two programs that I recommend: WinSCP for Windows and Cyberduck for OS X. To use SCP you need to enable SSH login on your server. And while you're at it you should disable FTP.
Write-protect your theme: There appears to be an exploit going around that modifies installed WordPress themes to add spam links or malicious iframes. One way to make this exploit more difficult is to modify the file permissions of your WordPress themes directory to 755 and the files within the directory to 644. The drawback is that you will now have to FTP modified files to your web server each time you want to make changes to your theme. Unfortunately you cannot apply the same write protection to the plugins directory since many plugins write data to the directory where it's installed.
View the HTML source of your site often: You should view the HTML source of your web site often. If you find chunks of encrypted JavaScript, embedded IFRAMEs or hidden links to sites you don't know, then your blog may have been compromised. The reason to do this often is so that you can discover any issue before Google does and blacklists you, or any of your readers get infected by malicious software distributed by your site.
