Hello dear readers , in this article I will write a few lines or safety tips on your site .
Basic dyes are some steps that you should always use to keep your website safe from those who want to harm your website .
1 ) Do you always use the update script .
Always do " Check Version " of Script to use , for example . vBulletin , phpBB , MyBB , wordpress , joomla ...
It is always important because new holes are discovered in these scripts , the most recent was the vBulletin 4.0.x which had a hole interesting " SQL Injection " , through a supplement to Firefox , the page gets injektoheshte can use this version of vBulletin , and displaying data and database Admin , if you are not careful and do not stay informed on these holes then you will receive being attacked . So whenever a new version comes out of the script do update it , because there will be many new things with less dangerous holes .
2 ) Use strong passwords .
Passwords like " 123456 " , " Chuang " etc. .. can always be detected because they have an easy character to be thinking , why not make it easy to love those you do badly , keep passwords of gravity. You can generate passwords from online sites that generate very strong passwords , here are some pages that can help you :
a) http://www.pctools.com/guides/password/
b ) http://strongpasswordgenerator.com/
c ) http://www.techzoom.net/tools/password-generator.en
3 ) chmod folders .
Some scripts require full reading and writing during the installation , it is provided by the 777 code folderta important as inches or admin . So these folders we do chmod 755 or 644 . If your folders have full reading and writing then it would be easy for a ruthless to inject code on your website .
4 ) Use secure FTP .
Many of us use FileZilla as a tool for the ftp connection is established , but after every session we do with FileZilla ftp you need to delete history FileZilla to connect to , because if injektoheni with a simple keylogger then your information will be stolen , and certainly your page will be attacked .
Also we use strong passwords ftp , read the advice number 2 for more .
5 ) Protect the administrator folder
You definitely need to protect the folder where you manage your website , and use these below steps to protect it :
a) Change the name of the folder eg / admncp , such as using a folder / adm125845 .
b ) Make Password Protect , go to cpanel to " security " click " Password Protect Directories " and then enter your username & password and a title to protect the administrator folder .
6 ) Protect your config page .
We all config file you included your site because there are records of your database . And must protect the config to keep your website safe, create a . Htaccess with this code :
<Files name-i-config.php>
Order Deny , Allow
deny from all
< / files >
and upload the folder where your config page .
7 ) Do not use nulled script .
Nulled scripts are more risks , they contain many holes and I personally have often encountered in the shell , then a " hacker " has become nulled script and upload a shell to hide in and has spread everywhere .
Therefore I suggest you to think twice before using nulled scripts .
8 ) Backup
If the company where you are not doing hosted daily or weekly backup for customers , then would you suggest to make one backup site every week , because not known anything . Perhaps one way or another your site will be compromised and deleted all the files and then it would be a nice situation without . So you suggest to do backup and save it on your computer or on your USB .
9 ) Inform your staff .
Give your advice to staff about their safety , give advice by telling them some events that can happen to them during the moderation of the site , such an occurrence when a person had cloned your page or any other ilegal case in your page.
10 ) Host in a company that is secure .
Take some advice from your friends where to Host your site , because some hosting site does not have full assurance in their servers , and synlink attack suffered by you in your webpage . So you're sure you 're hosted on a server that is protected
No comments:
Post a Comment